Please address the comments from this code review:
## Overall Comments
- The direct import of `dart:io` in `luxmeter_state_provider.dart` will break web builds—use conditional imports or platform-agnostic abstractions to avoid build errors on non-native targets.
- There’s a lot of duplicated logic across `_handleUnsupportedPlatform`, `_handleSensorError`, and `_handleSensorNotAvailable`—consider unifying these into a single streamlined error‐handling flow to reduce repetition.
- The chart layout code repeats padding and reserved size calculations for different breakpoints—extract those values into helper constants or methods to improve readability and maintainability.

## Individual Comments

### Comment 1
<location> `lib/view/luxmeter_screen.dart:146` </location>
<code_context>
-                timeAxisLabel,
+    final reservedSizeLeft = screenWidth < 400 ? 27.0 : 30.0;
+    final reservedSizeRight = screenWidth < 400 ? 27.0 : 30.0;
+    return Padding(
+      padding: const EdgeInsets.only(right: 20.0),
+      child: LineChart(
+        LineChartData(
+          backgroundColor: Colors.black,
</code_context>

<issue_to_address>
Adding right padding to the chart may cause misalignment with other UI elements.

Consider using a responsive value or matching the card's padding to ensure consistent alignment across different screen sizes.

Suggested implementation:

```
    // Define a responsive horizontal padding, or use the card's padding value if available
    final horizontalPadding = screenWidth < 400 ? 12.0 : 20.0;

    return Padding(
      padding: EdgeInsets.only(right: horizontalPadding),

```

If the card's padding is defined elsewhere (e.g., as a constant or theme value), you should reference that value instead of defining `horizontalPadding` here. Also, consider applying the same `horizontalPadding` to the left side if you want symmetrical padding for better alignment.
</issue_to_address>